| 翻訳と辞書 |
| software map ： ウィキペディア英語版 |
software map
A software map represents static, dynamic, and evolutionary information of software systems and their software development processes by means of 2D or 3D map-oriented information visualization. It constitutes a fundamental concept and tool in software visualization, software analytics, and software diagnosis. Its primary applications include risk analysis for and monitoring of code quality, team activity, or software development progress 〔Monitoring Code Quality and Development Activity by Software Maps Johannes Bohnet and Döllner, Jürgen. In: Proceedings of the IEEE ACM ICSE Workshop on Managing Technical Debt, pp. 9-16, 2011.〕 and, generally, improving effectiveness of software engineering with respect to all related artifacts, processes, and stakeholders throughout the software engineering process and software maintenance.
== Motivation and Concepts ==
Software maps are applied in the context of software engineering: Complex, long-term software development projects are commonly faced by manifold difficulties such as the friction between completing system features and, at the same time, obtaining a high degree of code quality and software quality to ensure software maintenance of the system in the future.
In particular, "Maintaining complex software systems tends to be costly because developers spend a significant part of their time with trying to understand the system’s structure and behavior."〔J. Bohnet: ''Visualization of Execution Traces and its Application to Software Maintenance''. PhD thesis, Hasso-Plattner-Institut, University of Potsdam, 2011.〕 The key idea of software maps is to cope with that challenge and optimization problems by providing effective communication means to close the communication gap among the various stakeholders and information domains within software development projects and obtaining insights in the sense of information visualization.
Software maps take advantage of well-defined cartographic map techniques using the virtual 3D city model metaphor〔R. Wettel, M. Lanza: ''Visualizing Software Systems as Cities''. 4th IEEE international Workshop on Visualizing Software for Understanding and Analysis, 2007.〕 to express the underlying complex, abstract information space. The metaphor is required "since software has no physical shape, there is no natural mapping of software to a two-dimensional space".〔A. Kuhn , P. Loretan , O. Nierstrasz: ''Consistent Layout for Thematic Software Maps'', 2008.〕 Software maps are non-spatial maps that have to convert the hierarchy data and its attributes into a spatial representation.
抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』
■ウィキペディアで「software map」の詳細全文を読む
スポンサード リンク
| 翻訳と辞書 : 翻訳のためのインターネットリソース |
Copyright(C) kotoba.ne.jp 1997-2016. All Rights Reserved.
|
|